From: Junio C Hamano <gitster@pobox.com>
To: David Brown <git@davidb.org>
Cc: dhruva <dhruva@ymail.com>, GIT SCM <git@vger.kernel.org>,
Simon Hausmann <simon@lst.de>
Subject: Re: [PATCH] Optional shrinking of RCS keywords in git-p4
Date: Mon, 15 Sep 2008 00:43:50 -0700 [thread overview]
Message-ID: <7vy71tetvt.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080915063521.GA1533@linode.davidb.org> (David Brown's message of "Sun, 14 Sep 2008 23:35:21 -0700")
David Brown <git@davidb.org> writes:
> ... As far as I can tell, P4 completely
> ignores whatever the $Id: ...$ headers happen to be expanded to at the
> time of checking. You can put garbage there, and it check in fine.
> ...
> I guess it isn't a problem to make this optional in git-p4, but I
> don't think this patch is solving the right problem.
Hmm. I do not do p4, but what I am guessing is that there probably is a
configuration switch on the p4 side that lets you check in files with
"$Id: garbage $" in them, while dhruva hasn't turned that switch on.
It could be (1) not flipping the switch on is a user mistake and dhruva
can just flip it to fix his problem, or (2) the policy of dhruva's project
mandates the switch to stay off, and he needs the patch to work around the
issue.
I cannot judge which is the case myself, but if the situation is the
former, we would need a documentation to suggest that magic p4 switch as a
workaround that would work for everybody without hurting anybody. On the
other hadn, if the situation is the latter, we would need this patch in
addition to the suggestion of the magic p4 switch that the user _may_ be
able to flip depending on the project policy on the p4 side.
next prev parent reply other threads:[~2008-09-15 7:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 6:26 [PATCH] Optional shrinking of RCS keywords in git-p4 dhruva
2008-09-15 6:35 ` David Brown
2008-09-15 7:43 ` Junio C Hamano [this message]
2008-09-15 11:02 ` Tor Arvid Lund
2008-09-15 19:22 ` Daniel Barkalow
2008-09-16 4:12 ` David Brown
2008-09-16 12:58 ` Jing Xue
2008-09-16 17:12 ` Daniel Barkalow
2008-09-16 17:32 ` Daniel Barkalow
-- strict thread matches above, loose matches on Subject: below --
2008-09-19 2:56 dhruva
2008-09-16 13:33 dhruva
2008-09-16 4:53 dhruva
2008-09-16 17:26 ` Daniel Barkalow
2008-09-16 2:51 dhruva
2008-09-15 11:46 dhruva
2008-09-15 15:27 ` Tor Arvid Lund
2008-09-15 7:21 dhruva
2008-09-15 6:31 dhruva
2008-09-15 5:58 Dhruva Krishnamurthy
2008-09-15 6:09 ` David Brown
2008-09-15 6:17 ` 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=7vy71tetvt.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=dhruva@ymail.com \
--cc=git@davidb.org \
--cc=git@vger.kernel.org \
--cc=simon@lst.de \
/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).