git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Carlos Rica" <jasampler@gmail.com>
To: "Kristian Høgsberg" <krh@redhat.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Port git-tag.sh to C.
Date: Sat, 9 Jun 2007 03:58:32 +0200	[thread overview]
Message-ID: <1b46aba20706081858u7f18d9b2o5602db43d396c19@mail.gmail.com> (raw)
In-Reply-To: <11813427591137-git-send-email-krh@redhat.com>

2007/6/9, Kristian Høgsberg <krh@redhat.com>:
> Ok, here's an updated version that passes the test suite.  Johannes, I
> leave it to you and jasam to merge the bits you find useful, but as
> far as I see it, this conversion is complete, and there's enough other
> shell scripts to port.  My port doesn't pass jasam's test suite, it
> looks like he is expecting the -l glob to be a regexp, but the
> git-tag.sh I started from used shell globs.

That's a good proposal! I agree with your version for matching tag names,
apart from the fact that the code is more compact and readable that way.

I will review your code comparing it with mine and I will report
everything I feel. However, my desire is to get builtin-tag.c and its
tests t7400-tag.sh complete
in a few days or less, so I would appreciate every other correction
from you in order to get it ready faster.

> Anyways, it'd be nice if you or jasam could keep the list a little
> more in the loop with the SoC changes, it is where most of the
> development happens, after all.  What's next on your list?

You're right, the development will be more open than now was, I
usually ask questions in the IRC channel and obviously that's not the
best way to report my work to everybody.

Feel free to choose the script which you need to get replaced first,
or, depending on your urgency, you could ask me for one of them and I
would try to concentrate my efforts on it. Why do you started with
git-tag? For me, it was enough easy to begin with, perhaps you could
have other reasons.

Looking forward to work with you on that,

Carlos

  reply	other threads:[~2007-06-09  1:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 22:45 [PATCH] Port git-tag.sh to C Kristian Høgsberg
2007-06-09  1:58 ` Carlos Rica [this message]
2007-06-12  3:28   ` Daniel Barkalow
2007-06-12 12:41     ` git-fetch, was " Johannes Schindelin
2007-06-12 13:29       ` Julian Phillips
2007-06-12 16:51         ` Daniel Barkalow
2007-06-12 23:55         ` Daniel Barkalow
2007-06-13  0:27           ` Johannes Schindelin
2007-06-09 18:26 ` Junio C Hamano
2007-06-09 23:27   ` Kristian Høgsberg
2007-06-10 12:37     ` Robin Rosenberg
2007-06-10 21:36       ` Junio C Hamano
2007-06-10 22:13   ` Jeff King
2007-06-10 22:19     ` Junio C Hamano
2007-06-10 22:22       ` Jeff King
  -- strict thread matches above, loose matches on Subject: below --
2007-06-08 21:38 Kristian Høgsberg
2007-06-08 21:51 ` Johannes Schindelin
2007-06-08 22:05   ` Kristian Høgsberg
2007-06-08 22:07     ` Johannes Schindelin
2007-06-08 22:36     ` Carlos Rica
2007-06-08 22:39   ` Matthijs Melchior

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=1b46aba20706081858u7f18d9b2o5602db43d396c19@mail.gmail.com \
    --to=jasampler@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=krh@redhat.com \
    /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).