All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Jon Seymour <jon.seymour@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: A system administration use case for git
Date: Thu, 23 Apr 2009 12:38:09 +0200	[thread overview]
Message-ID: <49F04511.3070601@viscovery.net> (raw)
In-Reply-To: <20090423095533.GE13989@pengutronix.de>

Uwe Kleine-König schrieb:
> There is a practical problem though:  The filelist has to be sorted in a
> way that is not provided by ls, so:
> 
> 	ukleinek@cepheus:~/gsrc/linux-2.6/usr$ for f in $(ls -A); do printf "100644 %s\x00" $f; git hash-object $f | perl -n -e 'chomp; for $c (split(/(.{2})/)) { printf("%c", hex($c)) if $c }'; done | git hash-object -t tree -w --stdin
> 	a0a6efb3f1de956badc7607c7d372cc325a18846

Does ... $(LANG=C ls -A) ... make a difference for you?

But note that this is still not the whole story because, IIUC, in tree
objects directories are sorted as if they had a slash appended; i.e.
directory "foo" is sorted *after* file "foo.c", but *before* file "foo0".

-- Hannes

  reply	other threads:[~2009-04-23 10:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22  8:33 A system administration use case for git Jon Seymour
2009-04-22  8:48 ` Martin Langhoff
     [not found]   ` <2cfc40320904220208g5acc2200w6144668ba2da5a09@mail.gmail.com>
2009-04-22  9:22     ` Jon Seymour
2009-04-22 10:07       ` Martin Langhoff
2009-04-22 10:18         ` Jon Seymour
2009-04-23  9:55 ` Uwe Kleine-König
2009-04-23 10:38   ` Johannes Sixt [this message]
2009-04-23 11:39     ` Uwe Kleine-König

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=49F04511.3070601@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=git@vger.kernel.org \
    --cc=jon.seymour@gmail.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.