From: Mark Wielaard <mark@klomp.org>
To: frysk@sourceware.org
Subject: Re: Import
Date: Thu, 11 Oct 2007 11:59:00 -0000 [thread overview]
Message-ID: <1192103961.3843.20.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <20071011112459.29614.qmail@sourceware.org>
Argh, so much for my dual git/cvs usage...
On Thu, 2007-10-11 at 11:24 +0000, mark@sourceware.org wrote:
> CVSROOT: /cvs/frysk
> Module name: frysk-imports
> Changes by: mark@sourceware.org 2007-10-11 11:24:59
>
> Log message:
> Import of libunwind version 20071010
>
> Status:
>
> Vendor Tag: LIBUNWIND
> Release Tags: libunwind_20071010
> [...]
> N frysk-imports/libunwind/.git/FETCH_HEAD
> N frysk-imports/libunwind/.git/index
> N frysk-imports/libunwind/.git/config
> [... lots of object files ...]
> N frysk-imports/libunwind/.git/hooks/update
> N frysk-imports/libunwind/.git/hooks/commit-msg
> N frysk-imports/libunwind/.git/hooks/pre-commit
Whoops...
Luckily Tim was quick enough to restore the world to something sane on
sourceware. Apologies. And if you accidentially updated in the few
minutes these extra .git files were around please refresh your cvs
checkout.
Lesson learned: The equivalent to cvs export is git-archive. This gives
you a clean tar ball with all sources without the git tracking files.
Cheers,
Mark
next parent reply other threads:[~2007-10-11 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071011112459.29614.qmail@sourceware.org>
2007-10-11 11:59 ` Mark Wielaard [this message]
[not found] <20070201205654.14198.qmail@sourceware.org>
2007-02-02 14:00 ` Import Mark Wielaard
2007-02-02 17:32 ` Import Andrew Cagney
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=1192103961.3843.20.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.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.
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).