git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[RFC/PATCHv1 0/2] git-p4: possible RCS keyword fixes

From
Luke Diamand <luke@diamand.org>
Date
Feb 9, 2012, 11:03 UTC
Message-ID
<1328785409-30936-1-git-send-email-luke@diamand.org>
This contains a possible way to fixup RCS keyword woes in git-p4.

The first patch adds a test case to demonstrate the problem. It would be useful to get this into git proper.

The second patch shows a possible way to solve the problem, by patching up the RCS keywords in the p4 checked-out tree. This patch does not cover all cases and is poorly tested. I'd like to see if this seems like a plausible approach.

Luke Diamand (2):
  git-p4: add test case for RCS keywords
  git-p4: initial demonstration of possible RCS keyword fixup
 contrib/fast-import/git-p4 |   43 ++++++++++++++++++++++-
 t/t9810-git-p4-rcs.sh      |   82 ++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 123 insertions(+), 2 deletions(-)
 create mode 100755 t/t9810-git-p4-rcs.sh
-- 
1.7.9.rc2.128.gfce41.dirty
Next: Luke Diamand
Message 1 of 4 in “[RFC/PATCHv1 0/2] git-p4: possible RCS keyword fixes”
  1. Luke DiamandFeb 9, 2012
  2. 1/2 git-p4: add test case for RCS keywordsLuke Diamand, Feb 9, 2012
  3. Junio C HamanoFeb 9, 2012
  4. 2/2 git-p4: initial demonstration of possible RCS keyword fixupLuke Diamand, Feb 9, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.