+1
From: crowbar-bounces On Behalf Of Williams, J T
Sent: Friday, March 21, 2014 1:27 PM
To: j...@suse.de; crowbar
Subject: Re: [Crowbar] Removing branches fully merged into "master".
Dell - Internal Use - Confidential
I am not arguing the point that anything will be lost. I agree
al Message-
From: J. Daniel Schmidt [mailto:j...@suse.de]
Sent: Friday, March 21, 2014 9:23 AM
To: crowbar
Cc: Williams, J T; tboer...@suse.de; aspi...@suse.com
Subject: Re: [Crowbar] Removing branches fully merged into "master".
Just a short reply on behalf of Thomas:
On Friday 21
Just a short reply on behalf of Thomas:
On Friday 21 March 2014 08:43:57 j_t_willi...@dell.com wrote:
> 3) It is tested and validated that we are capable of recreating our
> releases.
You can recreate any branch at any time. Nothing will be lost.
> ยท Do not delete pebbles and fred - they a
j_t_willi...@dell.com (j_t_willi...@dell.com) wrote:
> Thomas,
> I have received word from our development teams. Here is the view our
> leadership team asserted that we need to address to ensure that we can
> quickly respond and support deployments in the field.
> We should not be taking chanc
o:tboer...@suse.de>;
aspi...@suse.com<mailto:aspi...@suse.com>
Cc: crowbar
Subject: Re: [Crowbar] Removing branches fully merged into "master".
Dell - Internal Use - Confidential
Thomas,
Give me another day to get a response from Dell's internal development team
before takin
Dell - Internal Use - Confidential
From: crowbar-bounces On Behalf Of Williams, J T
Sent: Wednesday, March 19, 2014 10:46 AM
To: tboer...@suse.de; aspi...@suse.com
Cc: crowbar
Subject: Re: [Crowbar] Removing branches fully merged into "master".
Dell - Internal Use - Confidential
Th
-John
-Original Message-
From: crowbar-bounces On Behalf Of Thomas Boerger
Sent: Tuesday, March 18, 2014 12:32 PM
To: Thomas Boerger
Cc: crowbar
Subject: Re: [Crowbar] Removing branches fully merged into "master".
Reminder: I want to start tagging and removing the mentioned branches tomorrow.
Reminder: I want to start tagging and removing the mentioned branches
tomorrow.
Quoting Thomas Boerger :
> I have created a Gist with all branches of all barclamps. There you can see
> what i think we should do with all these branches.
>
> https://gist.githubusercontent.com/tboerger/c959c41134cf
ther branch,
> > then it can't be converted to a tag can it?
> >
> >
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Chris
> >
> > Dell
> >
> > -Original Message-
> > From: crowbar-bounces On Behalf
the branch?
>
>
>
> If a branch has 1 change in it that is not included in any other branch,
> then it can't be converted to a tag can it?
>
>
>
>
>
> Thanks,
>
>
>
> Chris
>
> Dell
>
> -Original Message-
> From: crowbar-bounce
> It sounds like the recommendation for best practice is to convert the
> shipped branch to a tag once that branch is no longer supported? Is there
> a safe way to do this without risking losing the branch?
we wont loose anything. We simply create a tag of that branch and if somebody
think he ne
christopher_dearb...@dell.com (christopher_dearb...@dell.com) wrote:
> Disclaimer: I am not a github expert.
>
> Regarding branch lifecycle:
>
> 1. Work on the release being actively developed continues in a branch
>
> 2. When that release is shipped, another branch is made so that active
On Wednesday 12 March 2014 09:27:20 christopher_dearb...@dell.com wrote:
> Disclaimer: I am not a github expert.
>
> Regarding branch lifecycle:
>
> 1. Work on the release being actively developed continues in a branch
After it was "split of" from the main development branch, yes. As long i
included in any other branch, then
it can't be converted to a tag can it?
Thanks,
Chris
Dell
-Original Message-
From: crowbar-bounces On Behalf Of Sascha Peilicke
Sent: Wednesday, March 12, 2014 10:07 AM
To: crowbar
Subject: Re: [Crowbar] Removing branches fully merged into &q
On Wednesday 12 March 2014 13:59:57 Adam Spiers wrote:
> [BTW no need to send to both crowbar@dell.com and crow...@lists.us.dell.com]
> Sascha Peilicke (sasc...@mailbox.org) wrote:
> > On the other hand, seasoned developers with an eye for beauty are
> > consistently annoyed by the continued over-u
[BTW no need to send to both crowbar@dell.com and crow...@lists.us.dell.com]
Sascha Peilicke (sasc...@mailbox.org) wrote:
> On the other hand, seasoned developers with an eye for beauty are consistently
> annoyed by the continued over-use of Github.
I'd call it abuse or misuse of git rather than
On Wednesday 12 March 2014 08:36:03 christopher_dearb...@dell.com wrote:
> Hey guys,
>
> Unless there is a compelling reason for doing this (and I haven't heard
> one), I would propose that we leave everything as-is. I don't see a need
> for doing this.
I guess there are two aspects to it:
New
age-
> From: crowbar-bounces On Behalf Of Thomas Boerger
> Sent: Wednesday, March 12, 2014 9:25 AM
> To: crowbar
> Subject: Re: [Crowbar] Removing branches fully merged into "master".
>
> On Wednesday, March 12, 2014 11:03:21 AM Adam Spiers wrote:
> > That&#x
Thomas Boerger (tboer...@suse.de) wrote:
> On Wednesday, March 12, 2014 11:03:21 AM Adam Spiers wrote:
> > That's not true at all. There was plenty of interest in doing it, but
> > the final deletion got postponed due to other activities and holidays.
>
> Sure it's true... They only said that ther
day, March 12, 2014 9:25 AM
To: crowbar
Subject: Re: [Crowbar] Removing branches fully merged into "master".
On Wednesday, March 12, 2014 11:03:21 AM Adam Spiers wrote:
> That's not true at all. There was plenty of interest in doing it, but
> the final deletion got postpo
On Wednesday, March 12, 2014 11:03:21 AM Adam Spiers wrote:
> That's not true at all. There was plenty of interest in doing it, but
> the final deletion got postponed due to other activities and holidays.
Sure it's true... They only said that there are multiple poeple are on
holiday... And that
I have created a Gist with all branches of all barclamps. There you can see
what i think we should do with all these branches.
https://gist.githubusercontent.com/tboerger/c959c41134cf39c5f409/raw/d59b2d250b6fbd323747ef4fe6843326e8edfc0e/gistfile1.txt
I want to start with it on 19th March if nobo
Thomas Boerger (tboer...@suse.de) wrote:
> Guys, are you serious? we started this thread multiple months ago and nobody
> really cared about it.
That's not true at all. There was plenty of interest in doing it, but
the final deletion got postponed due to other activities and holidays.
> And now
Guys, are you serious? we started this thread multiple months ago and nobody
really cared about it. And now we need to create again multiple lists for
repositories you don't work with anymore?
And even if some of the old release branches need a bugfix you can easily
create branch out of the ta
6 AM
To: crowbar
Subject: Re: [Crowbar] Removing branches fully merged into "master".
Please can you post a full list of the branches you intend to delete, to ensure
there is no confusion over the expected impact. I think it would also be wise
to give everyone in all time zones a minim
tagged, branch is still needed in case a bug need to be fixed for a
Customer.
Thanks,
Arkady
-Original Message-
From: crowbar-bounces On Behalf Of Adam Spiers
Sent: Tuesday, March 11, 2014 8:06 AM
To: crowbar
Subject: Re: [Crowbar] Removing branches fully merged into "master".
Please can you post a full list of the branches you intend to delete,
to ensure there is no confusion over the expected impact. I think it
would also be wise to give everyone in all time zones a minimum of 24
hours to respond before taking action.
Thomas Boerger (tboer...@suse.de) wrote:
> Hi eve
I forgot the hadoop/mesa branches. Should it be enough to stay on the latest
versions here and create a tag for all the other branches?
I think it makes most sense to remove the pretty old release branches after
creating a tag to preserve the current state.
On Tuesday, March 11, 2014 11:44:17 A
Hi everybody,
as nobody else said something i would like to start removing old branches
tomorrow! So it's your last chance to say something if you would like to get a
copy of specific old branches. I will create tags for all the older release
branches except roxy, stoney and hydrogen.
Kind re
I am not in favor of making changes like this while we have so much outstanding
pull backlog.
From: Williams, J T
Sent: Friday, December 13, 2013 10:47 AM Central Standard Time
To: crowbar
Subject: Re: [Crowbar] Removing branches fully merged into "master".
Dell - Internal Use - Co
pic.
-John
-Original Message-
From: crowbar-bounces On Behalf Of Sascha Peilicke
Sent: Wednesday, December 04, 2013 8:12 AM
To: crowbar
Subject: Re: [Crowbar] Removing branches fully merged into "master".
On Wednesday 04 December 2013 12:32:58 Adam Spiers wrote:
> Comments inline
On Wednesday 04 December 2013 12:32:58 Adam Spiers wrote:
> Comments inline ...
>
> Sascha Peilicke (speili...@suse.com) wrote:
> > Hi there,
> >
> > here's a slightly edited per repository list of branches merged into their
> > master branch. All of those are behind master. In other words, those
Comments inline ...
Sascha Peilicke (speili...@suse.com) wrote:
> Hi there,
>
> here's a slightly edited per repository list of branches merged into their
> master branch. All of those are behind master. In other words, those are
> fully
> merged branches waiting to be cleaned up. So if nobody
Hi there,
here's a slightly edited per repository list of branches merged into their
master branch. All of those are behind master. In other words, those are fully
merged branches waiting to be cleaned up. So if nobody objects, I'd like to
drop those later this day.
Playing the same game aga
34 matches
Mail list logo
