From: fork0@t-online.de (Alex Riesen)
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: Petr Baudis <pasky@suse.cz>,
"J. Bruce Fields" <bfields@fieldses.org>,
git@vger.kernel.org
Subject: Re: Git BOF notes
Date: Sun, 23 Jul 2006 09:38:18 +0200 [thread overview]
Message-ID: <20060723073818.GA5822@steel.home> (raw)
In-Reply-To: <fcaeb9bf0607221312k2088658bqa45e622b7fe244e4@mail.gmail.com>
Nguyễn Thái Ngọc Duy, Sat, Jul 22, 2006 22:12:07 +0200:
> >> I don't know if there's a point in being so paranoid - it already makes
> >> things more painful than necessary. In the tracking branch, you just
> >> want to have what the other side has anyway, and if the other side
> >> decided to jump around, why would you care otherwise?
> >
> >But for the ones who do care, it is much harder to notice. Even if it is
> >a warning (it gets lost in crontab logs).
>
> Then create some lost+found branches for them?
if you copy files from ext3 to vfat, do you expect them to be found in
lost+found? Usually not, I believe. It should either fail or copy.
next prev parent reply other threads:[~2006-07-23 7:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 23:01 Git BOF notes Petr Baudis
2006-07-21 13:18 ` J. Bruce Fields
2006-07-21 14:42 ` Petr Baudis
2006-07-22 0:17 ` Johannes Schindelin
2006-07-22 3:22 ` Petr Baudis
2006-07-22 3:55 ` Johannes Schindelin
2006-07-22 19:16 ` Petr Baudis
2006-07-22 20:03 ` Timo Hirvonen
2006-07-23 22:53 ` Johannes Schindelin
2006-07-21 13:21 ` J. Bruce Fields
2006-07-21 14:31 ` Petr Baudis
2006-07-21 15:02 ` Alex Riesen
2006-07-22 20:12 ` Nguyễn Thái Ngọc Duy
2006-07-23 7:38 ` Alex Riesen [this message]
2006-07-24 9:06 ` Catalin Marinas
2006-07-24 11:47 ` Petr Baudis
2006-07-24 12:08 ` Nguyễn Thái Ngọc Duy
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=20060723073818.GA5822@steel.home \
--to=fork0@t-online.de \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=pclouds@gmail.com \
--cc=raa.lkml@gmail.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.
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.