[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Patch mgmt workflow proposal

also sprach Thomas Koch <thomas@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

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

  (msgid 20110801121946.GA575@fishbowl.rw.madduck.net)
  (msgid 20110801182015.GA3100@fishbowl.rw.madduck.net)

Feedback welcome, of course.

 .''`.   martin f. krafft <madduck@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 ~

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Reply to: