what do I need to learn to do this task?

[Dave S]

On Tue, May 13, 2014 at 2:02 AM, Michael Mossey <michaelmossey at gmail.com>wrote:

>  [...]
> My goal is to avoid cluttering logs with meaningless changesets. Can you
> give me some sense now of how that will happen or look?
>
>

> I'm already comfortable with merging.
>
>
You know, I actually would not worry about it at all.  I don't care a bit
about meaningless changesets in my repos.  I do understand that some people
feel it "doesn't look pretty".  For me, that's a minor concern.  I want to
be able to find particular revisions, and between the graph log and tags,
that's easy.  Also, grepping log messages.   I would focus on just the
basics for now.  As I've said up-thread, when you've got that down, you can
look at the clean-up options.

I have repos that are pretty tightly focused on files directly used in the
project they are for.  I also have a repo that keeps growing kitchen sinks.
 In that one, I've recently checked in history files (bash history command
output, doskey /h output, copy-paste from sqlite prompts, etc; I like to
remember things that work, and sometimes my memory needs help).

On another note, I have some code in a Mercurial repo that's going to be
checked in to the corporate SVN repo.  Currently, the changesets are
oriented to "get a little bit working, check it in".  But I when I send it
to the SVN repo, I want it to be in easily-reviewed doses.  I'm being
influenced by the conventions of patch submission among the Mercurial
developers.  So I'm going to "hg up" into the past, start a branch, and use
diff tools to make a new series of changesets that focus on one change at a
time.  Each of those c/s will be checked into the SVN repo.  But when
that's all done, what happens to my original c/s?   Nothing.  I haven't
decided if I'll mark that branch closed, or merge it into the new branch,
but there's no need for me to remove any of the old checkins.

Workflows very quite a bit among people who have discussed them here on the
list, so if you don't like my recommendations, I'll just lump it and go on.
 But I really think that this is the wrong time to worry about your
changesets being pretty.

/dps



-- 
test signature -- please apply at front gate on Tuesdays only.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140513/b6307874/attachment-0002.html>