From: Konstantin Khomoutov <kostix+git@007spb.ru>
To: shawn wilson <ag4ve.us@gmail.com>
Cc: Konstantin Khomoutov <kostix+git@007spb.ru>,
Git List <git@vger.kernel.org>
Subject: Re: split directories into branches
Date: Mon, 4 Jul 2016 21:29:26 +0300 [thread overview]
Message-ID: <20160704212926.919a267706a6fa5791c47726@domain007.com> (raw)
In-Reply-To: <CAH_OBie4dUB8WXfmKhLaezVKi0=LhnFw=wKJO1c3oUMA7VkYdw@mail.gmail.com>
On Mon, 4 Jul 2016 14:15:58 -0400
shawn wilson <ag4ve.us@gmail.com> wrote:
[...]
> > I know Git tracks content, not files (and directory) but still many
> > folks have "stable" directories for their files, assign certain
> > semantics to them etc. I've needed such transfers myself, and this
> > topic has been raised more than once by folks over there on the
> > git-users mailing list.
[...]
> Thanks for pointing out the users list - didn't notice it and sorry
> for posting a user question on a dev list.
I don't possess the official stance on this topic but AFAIK user-level
questions are fine on this list. The git-users mailing list was
created -- as I understand it -- because of three reasons: 1) it's
easier to post to; 2) you don't receive all the bug reports and patch
traffic irrelevant to mere mortals; 3) you have good chances to get
even RTFM questions answered (mostly by those who just had RTFM
recently), though I'd say stackoverflow is better at this one. ;-)
next prev parent reply other threads:[~2016-07-04 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 16:45 split directories into branches shawn wilson
2016-07-04 17:39 ` Konstantin Khomoutov
2016-07-04 18:15 ` shawn wilson
2016-07-04 18:29 ` Konstantin Khomoutov [this message]
2016-07-04 21:03 ` shawn wilson
2016-07-04 22:10 ` Andreas Schwab
2016-07-04 23:30 ` shawn wilson
2016-07-04 23:31 ` shawn wilson
2016-07-05 9:56 ` Konstantin Khomoutov
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=20160704212926.919a267706a6fa5791c47726@domain007.com \
--to=kostix+git@007spb.ru \
--cc=ag4ve.us@gmail.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).