From: Petr Baudis <pasky@ucw.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH 1/2] Introduce git-run-with-user-path helper program.
Date: Thu, 19 May 2005 01:24:08 +0200 [thread overview]
Message-ID: <20050518232408.GA18281@pasky.ji.cz> (raw)
In-Reply-To: <7vekc4nom5.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Thu, May 19, 2005 at 12:41:38AM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> told me that...
> >>>>> "PB" == Petr Baudis <pasky@ucw.cz> writes:
>
> >> $ pwd
> >> /usr/src/linux/fs
> >> $ git-run-with-user-path cg-commit -- ext?/Makefile
> >>
> >> would work.
>
> PB> Yes. But if you do just cg-commit in the subdirectory, it won't work.
>
> The point of git-run-with-user-path is that it canonicalizes and
> filters the paths, chdir(2)'s to GIT_PROJECT_TOP before running
> cg-commit. So when cg-commit starts in the above example,
>
> (1) its $cwd is /usr/src/linux and your .git subdirectory is
> right there in ./.git/
> (2) it gets fs/ext2/Makefile and fs/ext3/Makefile as arguments.
Yes. My point is that sometimes the Cogito commands have
directory-specific functionality even when called without any arguments.
$ pwd
/usr/src/linux
$ date >>README
$ cd fs
$ date >>Makefile
$ cg-commit
will commit only the fs/Makefile change.
> >> BTW, I am wondering if your choice of cg-commit as an example
> >> (as opposed to something else like diff or add) is a flamebait
> >> or just an innocent random example ;-)?
>
> PB> It was completely innocent. :-) How would it be a flamebait?
>
> <http://members.cox.net/junkio/per-file-commit.txt> ;-).
JIT's snapshotting makes up for it, I think. It has some beauty. :-)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
next prev parent reply other threads:[~2005-05-18 23:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 6:05 [PATCH 1/2] Introduce git-run-with-user-path helper program Junio C Hamano
2005-05-17 19:03 ` Petr Baudis
2005-05-17 19:27 ` Junio C Hamano
2005-05-17 20:35 ` Petr Baudis
2005-05-17 21:18 ` Junio C Hamano
2005-05-17 21:37 ` Petr Baudis
2005-05-17 22:13 ` Junio C Hamano
2005-05-18 21:33 ` Petr Baudis
2005-05-18 22:41 ` Junio C Hamano
2005-05-18 23:24 ` Petr Baudis [this message]
2005-05-18 23:56 ` Junio C Hamano
2005-05-19 0:34 ` Linus Torvalds
2005-05-19 20:35 ` Junio C Hamano
2005-05-19 7:40 ` Thomas Glanzmann
2005-05-19 8:23 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2005-05-16 6:04 [PATCH 0/2] Introducing git-run-with-user-path program Junio C Hamano
2005-05-16 23:21 ` Junio C Hamano
2005-05-16 23:40 ` [PATCH 1/2] Introduce git-run-with-user-path helper program Junio C Hamano
2005-05-17 4:15 ` Junio C Hamano
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=20050518232408.GA18281@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).