Re: [Q] Mark files for later commit?
- From
- Daniel Nyström <daniel.nystrom@timeterminal.se>
- Date
- Mar 29, 2011, 09:18 UTC
- Message-ID
- <AANLkTik33jiKipcv8d8tY_FXa2nE0BtBdi9vro0gkdQc@mail.gmail.com>
- In-Reply-To
- <7v8vvytldk.fsf@alter.siamese.dyndns.org>
Den 29 mars 2011 09:51 skrev Junio C Hamano <gitster@pobox.com>:
Show 11 quoted lines
>> Daniel Nyström <daniel.nystrom@timeterminal.se> writes: >>> How would you like a git feature like described above, marking files >>> for later inclusion? >> >> That does not sound like a feature but merely a source of confusion. > > If that is the case, then probably you shouldn't be even updating the > "changelog" file constantly to begin with. Instead, how about creating a > separate "changelog+" file that is not tracked, and keep its contents > maintained continuously so stuff won't be forgotten? When the time to > release comes, you can "mv changelog changelog", and commit it.
If we ignore this particular case, how would a "git hold <file>..." feature do? -- $ git status # On branch master # Changed but not updated: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: package/qt/qt.mk # # Changed but on hold: # (use "git add --holds <file>..." to update what will be committed) # # modified: CHANGES # no changes added to commit (use "git add" and/or "git commit -a") -- Would there be other use-cases?