On Wednesday, July 23, 2014 10:03:13 PM anatoly techtonik wrote: > On Mon, Jul 14, 2014 at 11:40 PM, Mark A. Flacy <[email protected]> wrote > > You can use the hg branch command to mark totally unrelated changesets in > > a > > repository as belonging to the same branch. IMO, that makes it weird. > > Does "unrelated" means with no common parent? I don't know - never practiced > such scenario. Have you tried it?
Just did. flacy@flacy:/tmp/test$ hg log -G @ changeset: 3:d7847d5e53ce | branch: barf | tag: tip | user: Mark A. Flacy <[email protected]> | date: Wed Jul 23 19:07:06 2014 -0500 | summary: Updated bleep | o changeset: 2:0179ff773bd4 | user: Mark A. Flacy <[email protected]> | date: Wed Jul 23 19:05:43 2014 -0500 | summary: Added ferd. | o changeset: 1:048e8dd9c8ec | branch: barf | user: Mark A. Flacy <[email protected]> | date: Wed Jul 23 19:03:57 2014 -0500 | summary: Added fred | o changeset: 0:8fa3c48321c8 user: Mark A. Flacy <[email protected]> date: Wed Jul 23 19:02:21 2014 -0500 summary: added bleep I toggled the branch between default and barf between each commit. I'll admit that I had to use "-f" to make this happen (so that's an improvement from my memory), but you can still do it. That's with hg 2.7.2. -- Mark A. Flacy _______________________________________________ Scons-dev mailing list [email protected] http://two.pairlist.net/mailman/listinfo/scons-dev
