From: Samuel Lijin <sxlijin@gmail.com>
To: Rm Beer <rmbeer2@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: I suggest a new feature: One copy from files
Date: Sun, 23 Apr 2017 23:02:34 -0500 [thread overview]
Message-ID: <CAJZjrdVyKcPCmPT8S=Spju_Q7KRjkm7AbP4H--pVdiY9qR=AhQ@mail.gmail.com> (raw)
In-Reply-To: <CAA0fXPu7s1-UQ-RBxvmPq0kGSsdt1wp9VJp7wNMZ_uE02RvCbw@mail.gmail.com>
...what?
I'm sorry, I have absolutely no idea what you're asking. You're going
to have to be a lot more specific with your description of the desired
behavior because as is, I have no idea what purpose your .gitonecopy
or .gitonelog would serve. I also have no idea what this has to do
with the binary files ignored by .gitignore.
It would probably make sense for you to describe a use case for this
as well, to help us understand why you want what you're asking for.
On Sun, Apr 23, 2017 at 10:47 PM, Rm Beer <rmbeer2@gmail.com> wrote:
> I have a several directories with binary files datas that is discard
> by .gitignore.
>
> I recommend make a new .gitonecopy or .gitonelog or something that
> take the directories with only 1 copy of last updated and not take
> history of files in the repository.
> Maybe anyone found other best method for apply this idea.
next prev parent reply other threads:[~2017-04-24 4:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 3:47 I suggest a new feature: One copy from files Rm Beer
2017-04-24 4:02 ` Samuel Lijin [this message]
[not found] ` <CAA0fXPsuSZsn3tfm=f0G7OP7bL0L=7GDy_WVqfAnhfBKonrHvg@mail.gmail.com>
[not found] ` <CAJZjrdXqD-fSCjC75bPgeYKUDH-XvGkpjGgSeoYu9NNhZyiN3w@mail.gmail.com>
[not found] ` <CAA0fXPvf5V3bALha-7fwTCt17OnXMDX-BjAz+jmXrsbK62BtCg@mail.gmail.com>
2017-04-24 5:28 ` Samuel Lijin
2017-04-24 6:13 ` Jacob Keller
[not found] ` <CAA0fXPtvxGydnSQfuB6OtYArPN3kb=sJDb3dnJrjdE-=2Hp5pw@mail.gmail.com>
2017-04-25 0:37 ` Jacob Keller
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='CAJZjrdVyKcPCmPT8S=Spju_Q7KRjkm7AbP4H--pVdiY9qR=AhQ@mail.gmail.com' \
--to=sxlijin@gmail.com \
--cc=git@vger.kernel.org \
--cc=rmbeer2@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 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).