git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	Felipe Contreras <felipe.contreras@gmail.com>
Subject: Re: [PATCH v2 00/11] sha1_name: improvements
Date: Tue, 7 May 2013 17:11:56 -0500	[thread overview]
Message-ID: <CAMP44s3-vVUB4VnZP4uBMLAbviV+BMTqDcbO_TxkX+5RE6cnSg@mail.gmail.com> (raw)
In-Reply-To: <1367963711-8722-1-git-send-email-felipe.contreras@gmail.com>

On Tue, May 7, 2013 at 4:55 PM, Felipe Contreras
<felipe.contreras@gmail.com> wrote:
> While trying to add support for the @ shortcut lots of cleanups arised. Here
> they are in a single series.
>
> Felipe Contreras (7):
>   tests: at-combinations: simplify setup
>   tests: at-combinations: check ref names directly
>   tests: at-combinations: improve nonsense()
>   sha1_name: remove no-op
>   sha1_name: remove unnecessary braces
>   sha1_name: avoid Yoda conditions
>   sha1_name: reorganize get_sha1_basic()
>
> Ramkumar Ramachandra (4):
>   tests: at-combinations: increase coverage
>   tests: at-combinations: @{N} versus HEAD@{N}
>   sha1_name: don't waste cycles in the @-parsing loop
>   sha1_name: check @{-N} errors sooner

When merging this series to the @ shortcut one, there will be
conflicts, this is how I propose fixing them:

                return len; /* syntax Ok, not enough switches */
-       if (0 < len && len == namelen)
+       if (len > 0 && len == namelen)
                return len; /* consumed all */
-       else if (0 < len)
...
++      else if (len > 0)
 +              return reinterpret(name, namelen, len, buf);

- check "@" new-two
- check "@@{u}" upstream-two
...
++check "@" ref refs/heads/new-branch
++check "@@{u}" ref refs/heads/upstream-branch

If that creates some kind of problem I would rather throw away this
series rather than the other one.

Cheers.

-- 
Felipe Contreras

  parent reply	other threads:[~2013-05-07 22:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07 21:55 [PATCH v2 00/11] sha1_name: improvements Felipe Contreras
2013-05-07 21:55 ` [PATCH v2 01/11] tests: at-combinations: simplify setup Felipe Contreras
2013-05-07 21:55 ` [PATCH v2 02/11] tests: at-combinations: check ref names directly Felipe Contreras
2013-05-08  5:55   ` Junio C Hamano
2013-05-08  6:03     ` Felipe Contreras
2013-05-07 21:55 ` [PATCH v2 03/11] tests: at-combinations: improve nonsense() Felipe Contreras
2013-05-08  5:55   ` Junio C Hamano
2013-05-08  6:49     ` Felipe Contreras
2013-05-07 21:55 ` [PATCH v2 04/11] tests: at-combinations: increase coverage Felipe Contreras
2013-05-07 21:55 ` [PATCH v2 05/11] tests: at-combinations: @{N} versus HEAD@{N} Felipe Contreras
2013-05-07 21:55 ` [PATCH v2 06/11] sha1_name: remove no-op Felipe Contreras
2013-05-07 21:55 ` [PATCH v2 07/11] sha1_name: remove unnecessary braces Felipe Contreras
2013-05-07 21:55 ` [PATCH v2 08/11] sha1_name: avoid Yoda conditions Felipe Contreras
2013-05-07 21:55 ` [PATCH v2 09/11] sha1_name: don't waste cycles in the @-parsing loop Felipe Contreras
2013-05-07 21:55 ` [PATCH v2 10/11] sha1_name: reorganize get_sha1_basic() Felipe Contreras
2013-05-08  7:39   ` Ramkumar Ramachandra
2013-05-08  7:42     ` Felipe Contreras
2013-05-08 18:18   ` Junio C Hamano
2013-05-08 18:41     ` Junio C Hamano
2013-05-08 20:39     ` Felipe Contreras
2013-05-08 21:51       ` Junio C Hamano
2013-05-08 22:06         ` Felipe Contreras
2013-05-07 21:55 ` [PATCH v2 11/11] sha1_name: check @{-N} errors sooner Felipe Contreras
2013-05-07 22:11 ` Felipe Contreras [this message]
2013-05-08  5:56   ` [PATCH v2 00/11] sha1_name: improvements Junio C Hamano
2013-05-08 10:44     ` Ramkumar Ramachandra

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=CAMP44s3-vVUB4VnZP4uBMLAbviV+BMTqDcbO_TxkX+5RE6cnSg@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=peff@peff.net \
    /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).