Diamond wrote:
> we probably can arrive at a conclusion that git itself isn't good
> at all for package management.
I don't think we can. Please stop the nonsense, at least until you
have created something superior to git.
//Peter
On 19 September 2014 10:13, Diamond wrote:
> P.S. As you see from description this option affects git performance.
> So, we probably can arrive at a conclusion that git itself isn't good
> at all for package management. Maybe there are better architectural
> decisions for that.
>
Well. Yes. You'
On 19 September 2014 07:33, Diamond wrote:
> Lets assume, that I don't want to scrap old ebuild yet. There's no git
> cp command. git mv is just git rm + git add. That's what does it look
> like (usual revbump with git add in reality):
>
> https://github.com/cerebrum/dr/commit/311df9b04d876f58474
On Thu, 18 Sep 2014 14:29:41 -0700
"W. Trevor King" wrote:
>
> So Git works great, and GitHub's web UI doesn't support all of Git's
> bells and whistles, so… switch to a different VCS? Personally, my
> conclusion is “just use Git from the command line”. It's not like
> you're abandoning long
On Fri, Sep 19, 2014 at 01:01:13AM +0400, Diamond wrote:
> On Thu, 18 Sep 2014 13:08:11 -0700 W. Trevor King wrote:
> > Git can check for copies if you like:
> >
> > $ git clone git://github.com/cerebrum/dr.git
> > $ cd dr/
> > $ git show --find-copies-harder 311df9b04
> > …
> > copy fro
On Thu, 18 Sep 2014 13:08:11 -0700
"W. Trevor King" wrote:
> Git can check for copies if you like:
>
> $ git clone git://github.com/cerebrum/dr.git
> $ cd dr/
> $ git show --find-copies-harder 311df9b04
> …
> copy from games-strategy/openra/openra-20140608.ebuild
> copy to games-stra
Diamond wrote:
> I stumbled over this problem when started to use git for packages.
Use git show -M to unstumble yourself.
//Peter
On Thu, 18 Sep 2014 16:00:59 -0400
Rich Freeman wrote:
> What would you propose? The problem you raise is just as much an
> issue with cvs. I don't get a continuous history across revbumps in
> cvs today, so I don't really see a problem with moving to git.
I don't know what to propose. I stumbl
On Thu, Sep 18, 2014 at 11:33:40PM +0400, Diamond wrote:
> Lets assume, that I don't want to scrap old ebuild yet. There's no git
> cp command. git mv is just git rm + git add. That's what does it look
> like (usual revbump with git add in reality):
> https://github.com/cerebrum/dr/commit/311df9b04
On Thu, Sep 18, 2014 at 3:33 PM, Diamond wrote:
> Lets assume, that I don't want to scrap old ebuild yet. There's no git
> cp command. git mv is just git rm + git add. That's what does it look
> like (usual revbump with git add in reality):
> https://github.com/cerebrum/dr/commit/311df9b04d876f584
On Thu, 18 Sep 2014 17:04:55 +1200
Kent Fredric wrote:
> What's more, you can in fact do:
>
> git mv foo-1.ebuild foo-2.ebuild
> git commit
>
> and you can still easily tell git to show that as a difference in a
> log.
>
> Example script to emulate this and example output:
> https://gist.githu
On Thu, Sep 18, 2014 at 1:53 PM, Ulrich Mueller wrote:
>> On Thu, 18 Sep 2014, Tobias Klausmann wrote:
>
>> However, one aspect of how ebuilds are written these days will
>> cause a non-trivial amount of merge commits that are not actually
>> useful in that sense.
>
Git can do merge conflict
> On Thu, 18 Sep 2014, Tobias Klausmann wrote:
> However, one aspect of how ebuilds are written these days will
> cause a non-trivial amount of merge commits that are not actually
> useful in that sense.
> This is due to the way keywording and stabilization work on an
> ebuild level. Since ke
Hi!
Since we're causing at least mild upheaval process-wise, I
thought I'd bring up a topic that will be exacerbated by the git
migration if it's not really addressed.
AIUI, we try to avoid merge conflicts, unless the merge is a
meaningful integration of divergent processes.
However, one aspect
Hello!
Below are some packages that I fail to take care of as needed and have
not been using myself for a while. Please take over whatever you have
interest in:
Latest Open bugs
app-text/xmlstarlet
hasufell:
>
> First draft and only the basic ebuild workflow.
>
I'm working out the rest here
https://wiki.gentoo.org/wiki/Gentoo_git_workflow#step_by_step_example_.28ebuild.29
16 matches
Mail list logo
