Hello Johannes,
Johannes Schindelin writes:
> On Fri, 13 Apr 2018, Jakub Narebski wrote:
>> Hallvard Breien Furuseth writes:
>>
>>> Also maybe it'll be worthwhile to generate .git/info/grafts in a local
>>> clone of the repo to get back easily visible history. No grafts in
>>> the original rep
Hi Kuba,
On Fri, 13 Apr 2018, Jakub Narebski wrote:
> Hallvard Breien Furuseth writes:
>
> > Also maybe it'll be worthwhile to generate .git/info/grafts in a local
> > clone of the repo to get back easily visible history. No grafts in
> > the original repo, grafts mess things up.
>
> Just a r
Hallvard Breien Furuseth writes:
> Also maybe it'll be worthwhile to generate .git/info/grafts in a local
> clone of the repo to get back easily visible history. No grafts in
> the original repo, grafts mess things up.
Just a reminder: modern Git has "git replace", a modern and safe
alternative
On 12. april 2018 23:07, Rafael Ascensao wrote:
Would initiating a repo with a empty root commit, tag it with 'base' then
use $ git rebase --onto base master@{30 days ago} master;
be viable?
No... my question was confused from the beginning. With such large files
I _shouldn't_ have history (or
Would initiating a repo with a empty root commit, tag it with 'base' then
use $ git rebase --onto base master@{30 days ago} master;
be viable?
The --orphan & tag is perhaps more robust, since it's "harder" to move
tags around.
--
Rafael Ascensão
On Thu, Apr 12 2018, Hallvard Breien Furuseth wrote:
> On 12. april 2018 20:47, Ævar Arnfjörð Bjarmason wrote:
>> 1. Create a backup.git repo
>> 2. Each time you make a backup, checkout a new orphan branch, see "git
>> checkout --orphan"
>> 3. You copy the files over, commit them, "git log" a
On 12. april 2018 20:47, Ævar Arnfjörð Bjarmason wrote:
1. Create a backup.git repo
2. Each time you make a backup, checkout a new orphan branch, see "git
checkout --orphan"
3. You copy the files over, commit them, "git log" at this point shows
one commit no matter if you've done this bef
On Thu, Apr 12 2018, Hallvard Breien Furuseth wrote:
> Can I use a shallow Git repo for file versioning, and regularly purge
> history older than e.g. 2 weeks? Purged data MUST NOT be recoverable.
>
> Or is there a backup tool based on shallow Git cloning which does this?
> Push/pull to another
8 matches
Mail list logo
