From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] package.deprecated: Create initial template
Date: Sat, 7 Dec 2019 22:46:13 +1300 [thread overview]
Message-ID: <20191207224613.365c5984@katipo2.lan> (raw)
In-Reply-To: <2cf18040c81c4eb0afbbf3282bacb150c80b572f.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
On Fri, 06 Dec 2019 10:03:23 +0100
Alexis Ballier <aballier@gentoo.org> wrote:
> (*) and force the use of some handy git options like only commit paths
> starting from cwd even if other files had been git added, which i never
> remember what is the git cli option for this
There isn't so much a CLI option, more, there's a parameter that "git
commit" takes which allows you to enumerate which paths to commit.
So:
git commit
Commits everything staged.
git commit .
Commits only CWD
But, with one important caveat:
git commit
Will only commit changes previously added with "git add" or whatever to
the index.
git commit .
Will commit *any* changes to anything in "." as long as they're
"tracked" by git.
But this is what repoman does anyway ;)
The doc line for this in "git help commit" is:
3. by listing files as arguments to the commit command (without
--interactive or --patch switch), in which case the commit will
ignore changes staged in the index, and instead record the current
content of the listed files (which must already be known to Git);
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-07 9:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 16:09 [gentoo-dev] [PATCH] package.deprecated: Create initial template Michał Górny
2019-12-05 16:36 ` Alexis Ballier
2019-12-05 16:53 ` William Hubbs
2019-12-05 17:11 ` Alexis Ballier
2019-12-07 10:34 ` Joonas Niilola
2019-12-05 17:39 ` Michał Górny
2019-12-05 17:59 ` Alexis Ballier
2019-12-05 18:04 ` Michał Górny
2019-12-05 19:12 ` Gerion Entrup
2019-12-05 22:00 ` Alexis Ballier
2019-12-06 8:23 ` Tim Harder
2019-12-06 9:03 ` Alexis Ballier
2019-12-06 9:33 ` Tim Harder
2019-12-06 10:50 ` Alexis Ballier
2019-12-06 15:41 ` Matt Turner
2019-12-06 15:46 ` Michael 'veremitz' Everitt
2019-12-06 16:28 ` Mike Gilbert
2019-12-06 17:57 ` Michael 'veremitz' Everitt
2019-12-06 16:29 ` Alexis Ballier
2019-12-06 17:58 ` Michael Orlitzky
2019-12-07 9:38 ` Kent Fredric
2019-12-07 9:46 ` Kent Fredric [this message]
2019-12-06 11:33 ` Michał Górny
2019-12-06 11:45 ` Tim Harder
2019-12-05 16:39 ` Andreas K. Huettel
2019-12-05 16:46 ` Matt Turner
2019-12-05 17:56 ` Mikle Kolyada
2019-12-05 19:01 ` Alec Warner
2019-12-05 23:37 ` Aaron Bauman
2019-12-06 0:36 ` Chí-Thanh Christopher Nguyễn
2019-12-06 7:15 ` Michał Górny
2019-12-06 7:35 ` Tim Harder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191207224613.365c5984@katipo2.lan \
--to=kentnl@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox