From: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
To: git@vger.kernel.org
Subject: Re: [PATCH 1/2] Introduce git-run-with-user-path helper program.
Date: Thu, 19 May 2005 09:40:07 +0200 [thread overview]
Message-ID: <20050519074007.GI4738@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <20050518232408.GA18281@pasky.ji.cz>
Hello,
> > <http://members.cox.net/junkio/per-file-commit.txt> ;-).
> I think the workflow that involves per-file commit is
> fundamentally broken at two levels.
I disagree here. We at FAUmachine often have FLAGS to turn on specific
features or debugging output by tweaking a headerfile. However we commit
often and work in small steps (at the moment using CVS because every
developer has write access). And we definitely don't want to tweak the
header file every time we commit, so I often do a:
cvs diff > diff
vim diff
lsdiff diff
cvs commit <interesting files here>
Thomas
next prev parent reply other threads:[~2005-05-19 7:39 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
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 [this message]
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=20050519074007.GI4738@cip.informatik.uni-erlangen.de \
--to=sithglan@stud.uni-erlangen.de \
--cc=git@vger.kernel.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).