Patch mgmt workflow proposal

[martin f krafft]

also sprach Thomas Koch <thomas at koch.ro> [2011.08.01.1914 +0200]:
> So as a variation of the described workflow you can establish
> a special branch that holds references to all feature branch
> commits in its history.

This comes about ¾ of the way to the history pollution done by
TopGit. Not only would users potentially get confused by this
additional branch (which is an implementation detail), it would also
get in the way in gitk output (cf. pristine-tar) and annoy even the
unconfused.

I am currently investigating means to store information outside the
worktree in an immutable and automatically tracked-and-shared way:

  http://permalink.gmane.org/gmane.comp.version-control.git/178349
  (msgid 20110801121946.GA575 at fishbowl.rw.madduck.net)
  http://permalink.gmane.org/gmane.comp.version-control.git/178393
  (msgid 20110801182015.GA3100 at fishbowl.rw.madduck.net)

Feedback welcome, of course.

-- 
 .''`.   martin f. krafft <madduck at d.o>      Related projects:
: :'  :  proud Debian developer               http://debiansystem.info
`. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
 
there is no place like ~
-------------- next part --------------
A non-text attachment was scrubbed...
Name: digital_signature_gpg.asc
Type: application/pgp-signature
Size: 1124 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
URL: <http://lists.alioth.debian.org/pipermail/vcs-pkg-discuss/attachments/20110801/b08040e1/attachment.pgp>