On 10/18/06, Petr Baudis wrote:
Yes and no, The bundle includes both the full final thing, and each
step along the way. Each step along the way is something you'll get
when you merge it.
Once merged, it will be "next one" in the description above. It would
typically look something like this in "bzr log"(shortened) In this
example, doing C requires doing A and B as well...
committer: foobar@foobar.com
message: merged in C
-------
committer: bar@bar.com
message: opps, fix bug in A
-------
committer: bar@bar.com
message: implement B
-------
committer: bar@bar.com
message: implement A
So, you'll get full history, including errors made :) You can also
see who approved it to this branch (foobar) and who did the actual
work (bar)
/Erik
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| James Bottomley | Re: Integration of SCST in the mainstream Linux kernel |
| Robin Lee Powell | NFS hang + umount -f: better behaviour requested. |
git: | |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| Gerrit Renker | [PATCH 18/37] dccp: Support for Mandatory options |
