From: NP-Hardass <NP-Hardass@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: Call for agenda items - Council meeting 2016-04-10
Date: Mon, 4 Apr 2016 09:11:45 -0400 [thread overview]
Message-ID: <57026811.9010302@gentoo.org> (raw)
In-Reply-To: <CAGfcS_kO5N-wGNmnmFfZKMoHFMawtBu5q1jfdgw86LNk8EW6uQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 04/04/2016 05:24 AM, Rich Freeman wrote:
> On Sun, Apr 3, 2016 at 10:27 PM, NP-Hardass <NP-Hardass@gentoo.org>
> wrote:
>>
>> An aside: Part of the git migration was converting the cvs
>> history to git to be available as a graft point [1][2].
>> Regardless of whether this is to ultimately become the canonical
>> means of looking up a package's changelog, can we document how
>> the graft is supposed to be done/configure the repo accordingly?
>> I'm completely unfamiliar with git grafting, but [3] suggests
>> that there should be an entry in .git/info/grafts.
>
> https://wiki.gentoo.org/wiki/Gentoo_git_workflow#Grafting_Gentoo_histo
ry_onto_the_active_repository
>
>
>> Since I'm unfamiliar with grafting, is there a reason why we
>> don't ship the repo with this file populated to begin with
>
> It is a reference, and if you fetch/clone a git repo you only get
> the references you explicitly ask for. I've actually tried pushing
> the reference and while that works you don't get it when you clone
> unless you ask for it, which is the same effort as just re-creating
> it.
>
Ah. Thanks so much. Greatly appreciate the info/resources. Didn't
realize that the info was on the wiki.
- --
NP-Hardass
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJXAmgRAAoJEBzZQR2yrxj7wHUQAJoQxieMDHbR0gdfv0Ejp/G3
qacdcLm8CjmJTbRM4jpP67uHtWuNalDJ++Do/7srMppFq++wI/z8epQiXlDT3EYS
LD4DRFwvZXMMFYsJXmTDR+0lQYSCx/85jA+IJHuKYKHiINVTT3lQ2DmeIguhgE7X
nleFSTKReqK6safHurDCSJ3/iU8RUSRfhdOf3Gq5YY3YE4wG3kHy15Ih0Gdo9c8H
ZkVYlTRYCahd+7oGbd7oef/YI7M+PRvz+McqSx7o6xIVpZg0lQSWe6WLn97OAvc2
G3yh/LyCByTveavGErgpZsVDZTbO74kETGF0UmmuQi35yqp8FAWRumqSypOxAUyn
NE3Kvp92M6thTDjonO8sSql4QtQ+mYfsZ1/yTCBy7K35Dj3gOWLLhTlbdwIJM/qb
KbicUg4Q1+ojyw31x+Hag4tAn9b1JNpIdxh6/vdJ1jauFpYXVG/S2AMQchtMxo15
DlW9BsMsxbXtlzdmjNNCela4/q9eWyT5ztb0M2r43V+/6FSknWF0SBBucwD9hqmM
7ZLks4rHexAiH1sdGTEWOniEFerIJTRb0GjYUryrNQlJh4OrEtfr5I4vHJ7DUQvk
nrnO/YCSLqJkF+3C0kiaUjavs6Uymt9qqW7G1GgiwkcrOUPE+NrHaScWjnZGFdAo
q5lHytItr4i84mZlrcH5
=okrV
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-04-04 13:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 20:00 [gentoo-project] Call for agenda items - Council meeting 2016-04-10 Ulrich Mueller
2016-03-27 21:13 ` Michał Górny
2016-04-03 18:07 ` [gentoo-project] " Ulrich Mueller
2016-04-03 18:40 ` Rich Freeman
2016-04-03 20:06 ` Matthew Thode
2016-04-04 7:01 ` Andrew Savchenko
2016-04-04 9:29 ` Rich Freeman
2016-04-05 6:59 ` Andrew Savchenko
2016-04-05 7:53 ` Patrick Lauer
2016-04-05 9:40 ` Rich Freeman
2016-04-03 20:32 ` Ulrich Mueller
2016-04-03 22:55 ` Rich Freeman
2016-04-04 2:27 ` NP-Hardass
2016-04-04 9:24 ` Rich Freeman
2016-04-04 13:11 ` NP-Hardass [this message]
2016-04-05 9:37 ` [gentoo-project] " Alexis Ballier
2016-04-05 9:59 ` Patrick Lauer
2016-04-05 10:03 ` Alexis Ballier
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=57026811.9010302@gentoo.org \
--to=np-hardass@gentoo.org \
--cc=gentoo-project@lists.gentoo.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