From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"Rhodes, Kate" <masukomi@gmail.com>,
git@vger.kernel.org
Subject: Re: ambiguous git-log date and timestamp syntax
Date: Sun, 2 Mar 2008 14:40:52 +0000 (GMT) [thread overview]
Message-ID: <alpine.LSU.1.00.0803021438010.22527@racer.site> (raw)
In-Reply-To: <200803021040.55252.jnareb@gmail.com>
Hi,
On Sun, 2 Mar 2008, Jakub Narebski wrote:
> I wonder if it would be worthwhile to extract all those useful codelets
> (mini libraries) like approxidate, strbuf, parseopt, ALLOC_GROW, list
> utils, etc. into separate micro-projects, to be able to be used by other
> projects, for *them* not to have to reimplement the wheel.
Actually, something like this happens in git-cheetah ATM, where I would
like to use parts of libgit.a to call programs.
But then, I see the responsibility of separating out parts of libgit.a by
those who want to use it, not by the git crowd.
Ciao,
Dscho
next prev parent reply other threads:[~2008-03-02 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 16:15 ambiguous git-log date and timestamp syntax Rhodes, Kate
2008-03-01 17:10 ` Jakub Narebski
2008-03-01 21:46 ` Linus Torvalds
2008-03-01 22:26 ` Jakub Narebski
2008-03-02 2:44 ` Johannes Schindelin
2008-03-02 9:40 ` Jakub Narebski
2008-03-02 14:40 ` Johannes Schindelin [this message]
2008-03-02 7:09 ` Florian Weimer
2008-03-02 14:11 ` [PATCH] Documentation: Remove --{min,max}-age option from git-log(1) 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LSU.1.00.0803021438010.22527@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=masukomi@gmail.com \
--cc=torvalds@linux-foundation.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).