From: Alexander Potashev <aspotashev@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2009, #02; Sun, 11)
Date: Sun, 11 Jan 2009 15:21:28 +0300 [thread overview]
Message-ID: <20090111122128.GA16108@myhost> (raw)
In-Reply-To: <7v63kmtbk6.fsf@gitster.siamese.dyndns.org>
On 01:51 Sun 11 Jan , Junio C Hamano wrote:
> [New Topics]
>
> Need to clean up the log message, perhaps rebase it to maint-1.6.0 and
> start cooking in 'next'.
>
> * jc/maint-format-patch (Sat Jan 10 12:41:33 2009 -0800) 1 commit
> + format-patch: show patch text for the root commit
My testcases ([PATCH] Add new testcases for format-patch root commits)
for this don't satisfy the target behaviour.
>
> All of the above 'pu' topics are ready for 'next'.
>
> * ap/clone-into-empty (Fri Jan 9 02:24:23 2009 +0300) 2 commits
> - Use is_pseudo_dir_name everywhere
> - Allow cloning to an existing empty directory
As far as I understood from your message, you don't think that cloning
into empty directories is necessary. So, I thought, the best solution for
yesterday was "[PATCH] add is_dot_or_dotdot inline function" (to make you
happy ;)).
But the workarounds like this:
| $ git clone -n $there it.git
| $ mv it.git/.git . && rmdir it.git && git checkout -f
are painful, especially for newbies who have no idea about anything but
'git clone'.
>
> There is an updated patch that only refactors the repeated code to check
> if a dirent is dot or dot-dot posted, which I should have picked up to
> replace these but I haven't yet (the "clone into empty" can and should
> build on top of it).
>
Btw, I've sent some worthwhile patches, I but haven't got any reply from you:
[PATCH] use || instead of | in logical expressions
[PATCH] Replace deprecated dashed git commands in usage
[PATCH] remove unnecessary 'if'
It's better if you say "No" than nothing.
next prev parent reply other threads:[~2009-01-11 12:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 9:51 What's cooking in git.git (Jan 2009, #02; Sun, 11) Junio C Hamano
2009-01-11 12:21 ` Alexander Potashev [this message]
2009-01-11 20:24 ` Junio C Hamano
2009-01-11 14:33 ` Jakub Narebski
2009-01-11 22:19 ` Junio C Hamano
2009-01-12 1:25 ` Jakub Narebski
2009-01-12 1:41 ` Junio C Hamano
2009-01-21 14:28 ` Sebastien Cevey
2009-01-23 12:04 ` Jakub Narebski
2009-01-12 1:58 ` Marcel Koeppen
2009-01-12 4:03 ` Junio C Hamano
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=20090111122128.GA16108@myhost \
--to=aspotashev@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).