Junichi Uekawa wrote: > At Mon, 16 Jul 2007 21:39:21 +0100, > Adam D. Barratt wrote: >> You're receiving this e-mail as you've recently (for relative values of >> "recently" :-) submitted a request to modify the way that debcommit >> handles git repositories. >> >> I'm not a git user myself as yet, so apologise if I'm overlooking >> something but it looks as if some of the changes requested are >> incompatible with each other. If it's possible to produce a patch that >> each of you are happy with (or as many as we can realistically manage) >> I'll happily apply it. >> >> As it's the most recent, I'll use Martin's patch as a starting point - >> Jamey, Josh and Junichi, would applying the patch proposed in >> http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;att=0;bug=433081 >> provide you with the functionality you'd expect / want from using >> debcommit against git repositories? > > As I commented, use of '--cached' will make debcommit work differently > for 'git' compared to other SCMs; I thought I proposed a patch and > made an attachment.
"git commit" behaves differently than other SCMs. If I use debcommit with Git, I don't expect consistency with other SCMs; I expect consistency with Git. debcommit should always behave like the default commit command of the version control system in use. I believe debcommit should continue using --cached, and simply needs to stop using git commit -a. - Josh Triplett
signature.asc
Description: OpenPGP digital signature
