From: Francis Galiegue <fg@one2team.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: Need help for migration from CVS to git in one go (ie, FORGETTING CVS history)
Date: Thu, 6 Nov 2008 02:15:40 +0100 [thread overview]
Message-ID: <200811060215.40869.fg@one2team.net> (raw)
In-Reply-To: <20081105235035.GA10544@machine.or.cz>
Le Thursday 06 November 2008 00:50:35 Petr Baudis, vous avez écrit :
> Hi,
>
> On Thu, Nov 06, 2008 at 12:14:56AM +0100, Francis Galiegue wrote:
> > * second: even though this may be a "non problem", we use Bonsai, which
> > has the ability to see what was commited by whom, given a time interval
> > (from d1 to d2): the base gitweb allows to search by commiter, which is
> > good, but it has no date boundaries: do tools exist for git that can do
> > this? If not, that wouldn't be a big deal, however...
>
> git log --since='2 months ago' --until='1 month ago'
>
> There is no gitweb functionality for this right now, but I think an
> implementation of that would be welcome in principle.
>
Well, right now, the search field is only a... field. Implementing such a
change would require a whole search page... I don't think anyone would want
to pollute the bare-bones page with more fields if they're of no use 90+% of
the time.
A search page would make sense, I guess, since the date criterion is not the
only one that you could use... But what other criteria would be useful? And
then, if a search page is implemented, what of the current dropdown list?
Drop it altogether and put a "Search commits..." link instead?
> > * third: also Bonsai-related; Bonsai can link to Bugzilla by matching
> > (wild guess) /\b(?:#?)(\d+)\b/ and transforming this into
> > http://your.bugzilla.fqdn.here/show_bug.cgi?id=$1. Does gitweb have this
> > built-in? (haven't looked yet) Is this planned, or has it been discussed
> > and been considered not worth the hassle?
>
> This is planned and I think there are third-party patches for this
> (cannot find them quickly, though), but upstream gitweb does not have
> the support for this included yet.
I'd love to have a link to these patches, honestly. "Our" commit messages are
poor enough that more often than not, the whole commit message is, for
instance, "fix bug #xxxx". While I push hard for more explicit commit
messages, this is just a pipe dream and that link to Bugzilla is vital to
us...
--
fge
next prev parent reply other threads:[~2008-11-06 1:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 23:14 Need help for migration from CVS to git in one go (ie, FORGETTING CVS history) Francis Galiegue
2008-11-05 23:23 ` Shawn O. Pearce
2008-11-05 23:34 ` Francis Galiegue
2008-11-05 23:44 ` Shawn O. Pearce
2008-11-06 1:28 ` Francis Galiegue
2008-11-06 21:18 ` Robin Rosenberg
2008-11-05 23:50 ` Petr Baudis
2008-11-06 1:15 ` Francis Galiegue [this message]
2008-11-06 3:08 ` Jakub Narebski
2008-11-06 12:13 ` Francis Galiegue
2008-11-07 0:34 ` Jakub Narebski
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=200811060215.40869.fg@one2team.net \
--to=fg@one2team.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.