From: "Adeodato Simó" <dato@net.com.org.es>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] contrib/workdir: create logs/refs and rr-cache in the origin repository
Date: Mon, 19 Jan 2009 13:20:18 +0100 [thread overview]
Message-ID: <20090119122018.GA25566@chistera.yi.org> (raw)
In-Reply-To: <7vskngwfko.fsf@gitster.siamese.dyndns.org>
* Junio C Hamano [Sun, 18 Jan 2009 11:59:35 -0800]:
> Adeodato Simó <dato@net.com.org.es> writes:
> > However, I've as of late directly created bare repositories knowing that
> > I wanted to work just with workdirs against it. In this case, the logs
> > for each checkout'ed branch will be stored in the workdirs and not the
> > repo, so deleting the workdir will make you lose those logs. Which is
> > bad, since workdirs should always be safe to delete.
> I had to think about the above for a while, but after realizing that you
> have a strict distinction between a "workdir" and a normal "repository
> with a work tree" in mind, I can see where you are coming from. A workdir
> is transient in nature and you should be able to dismiss it safely as long
> as the repository it borrows from is intact.
The thing, for me, is that a workdir should result in effects as close
as possible as doing the work in the repository with the workdir itself.
I normally use workdirs when it's not feasible to do the work in the
repo itself (eg., there's work in progress I'd rather have around,
rather than committing it to a temporary branch, to leave the repo
"clean" for further work).
> A workdir is a new work area that is not a normal "work tree with a
> full repository", but borrows from an existing repository. Any side
> effect from the work you do in a workdir will be saved in the original
> repository, and removing one would lose only the three kind of
> information listed above. Creating a new workdir has the side effect
> of enabling reflogs and rerere in the original repository.
> But the last sentence somehow feels dirty.
I really don't understand that last sentence. Does "mkdir logs/refs rr-cache"
*enable* reflogs and rerere at all? Or, rather, it just gives an empty
space for the workdirs "connecting" to it to save their reflogs and
rerere stuff iff they are configured to do so?
Cheers,
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
Love in your heart wasn't put there to stay.
Love isn't love 'til you give it away.
-- Oscar Hammerstein II
next prev parent reply other threads:[~2009-01-19 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 16:15 [PATCH] contrib/workdir: create logs/refs and rr-cache in the origin repository Adeodato Simó
2009-01-18 1:31 ` Junio C Hamano
2009-01-18 11:38 ` Adeodato Simó
2009-01-18 19:59 ` Junio C Hamano
2009-01-19 12:20 ` Adeodato Simó [this message]
2009-01-19 19:48 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090119122018.GA25566@chistera.yi.org \
--to=dato@net.com.org.es \
--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.
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 NNTP newsgroup(s).