On Wed, 2007-07-18 at 09:10 +0900, Junichi Uekawa wrote
[...]
> > > Comments?
> > >
> > > This will need modification in the manual, and will have an
> > > undecided behavior for 'debcommit' for other SCMs. I would
> > > suggest making debcommit do nothing, or implicitly do '-a'. Of
> > > course
also sprach Junichi Uekawa <[EMAIL PROTECTED]> [2007.07.17.1535 +0200]:
> So, you're proposing the following workflow is better
>
> git-add XXX
> git-add YYY
> git-status (check what's going to be committed)
> git-diff --cached (check the actual diff to be committed)
> debcommi
also sprach Junichi Uekawa <[EMAIL PROTECTED]> [2007.07.17.0113 +0200]:
> 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 works differently wrt other SCMs anyway in that it exposes
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 so
At Mon, 16 Jul 2007 21:39:21 +0100,
Adam D. Barratt wrote:
>
> Hi,
>
> 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
Hi,
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 ar
6 matches
Mail list logo