From: Samuel Lijin <sxlijin@gmail.com>
To: Rm Beer <rmbeer2@gmail.com>, "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: I suggest a new feature: One copy from files
Date: Mon, 24 Apr 2017 00:28:37 -0500 [thread overview]
Message-ID: <CAJZjrdXWbBz3MUVG4WuXvkGD1TZDWTaaEd7VXnyhDsXvU7WSEw@mail.gmail.com> (raw)
In-Reply-To: <CAA0fXPvf5V3bALha-7fwTCt17OnXMDX-BjAz+jmXrsbK62BtCg@mail.gmail.com>
Looping the listserv back in, didn't realize this had gone off thread.
I'm not sure what you mean by "update only the last change, and not
record the old changes".
update-index is, like most Git commands, per repo.
On Mon, Apr 24, 2017 at 12:08 AM, Rm Beer <rmbeer2@gmail.com> wrote:
> Yes, but i say about of have a update only the last change, and not
> record the old changes. Interesting command the 'update-index', this
> is a permanent config for each dir/files?
>
> 2017-04-24 1:59 GMT-03:00 Samuel Lijin <sxlijin@gmail.com>:
>> Ah - I see what you're asking for now, basically the ability to tell Git to
>> ignore changes to a file once you've already started tracking it, right?
>>
>> If I'm not mistaken, git update-index --skip-worktree will do this for you.
>> (I'm on my phone, so I don't have easy access to documentation right now.)
>>
>> Hope this helps.
>>
>> On Apr 23, 2017 11:51 PM, "Rm Beer" <rmbeer2@gmail.com> wrote:
>>>
>>> in a repository have two behaviors. (How understand i)
>>>
>>> 1) A file can check and updated in the repository, take any change
>>> from the file like a record logs.
>>> 2) If the file have in .gitignore . Git never see it.
>>>
>>> I suggest add a new behaviors:
>>>
>>> 3) A file can check and updated in the repository. But never add in
>>> the record logs, only have one copy in the repository. (Maybe add
>>> filters in .gitonecopy or something)
>>>
>>>
>>> 2017-04-24 1:02 GMT-03:00 Samuel Lijin <sxlijin@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 5:29 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
[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 [this message]
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=CAJZjrdXWbBz3MUVG4WuXvkGD1TZDWTaaEd7VXnyhDsXvU7WSEw@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).