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

Re: [PATCHv3 1/2] t5520-pull: Add testcases showing spurious conflicts from git pull --rebase

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Aug 9, 2010, 20:35 UTC
Message-ID
<AANLkTinDK4GZ2GamqZHvx6+Cu5eVD1EncizKVxMONuek@mail.gmail.com>
In-Reply-To
<AANLkTin0xvK8H8RvaXtmaNHJh1dStn0AN1Mqed7JGvuO@mail.gmail.com>
On Mon, Aug 9, 2010 at 19:22, Elijah Newren <newren@gmail.com> wrote:
Show 17 quoted lines
> On Mon, Aug 9, 2010 at 1:09 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Elijah Newren <newren@gmail.com> writes:
> <snip>
>>> +modify () {
>>> +     sed -e "$1" < "$2" > "$2".x &&
>>> +     mv "$2".x "$2"
>>> +}
>>
>> Just a style thing but I'd prefer to see the above written like this:
>>
>>        modify () {
>>                sed -e "$1" <"$2" >"$2.x" &&
>>                mv "$2.x" "$2"
>>        }
>
> I copied this function verbatim from t/t4127-apply-same-fn.sh.  Would
> you like me to fix that one too?

Rather than copy-paste this around we should just turn it into a utility function.

It'd be very useful (if you're up to it) to just use sed in this patch, then submit another patch to include the modify() function in the test-lib.sh (and document it in t/README).

These could also use a modify():
    cd t && grep -A1 sed  *sh | grep -B1 mv | less
Previous: Elijah NewrenNext: Elijah Newren
Message 6 of 7 in “[PATCHv3 0/2] Fix spurious conflicts with pull --rebase”
  1. Elijah NewrenAug 8, 2010
  2. 1/2 t5520-pull: Add testcases showing spurious conflicts from git pull --rebaseElijah Newren, Aug 8, 2010
  3. Elijah NewrenAug 9, 2010
  4. Junio C HamanoAug 9, 2010
  5. Elijah NewrenAug 9, 2010
  6. Ævar Arnfjörð BjarmasonAug 9, 2010
  7. 2/2 pull --rebase: Avoid spurious conflicts and reapplying unnecessary patchesElijah Newren, Aug 8, 2010

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.