On Fri, Jul 22, 2016 at 10:57 PM, Nicolas Passerini
wrote:
> In Iceberg you currently can:
>
> 1) Download a project using metacello github:// protocol
> 2) Use Iceberg to make it "writable" (i.e. transform it to an Iceberg
> repository, pointing to the same remote
In Iceberg you currently can:
1) Download a project using metacello github:// protocol
2) Use Iceberg to make it "writable" (i.e. transform it to an Iceberg
repository, pointing to the same remote repository), this is just one step.
3) Commit and push using the new repo, etc.
What it is not done
On 07/22/2016 07:11 AM, Peter Uhnak wrote:
On Fri, Jul 22, 2016 at 09:14:25PM +0800, Ben Coman wrote:
On Fri, Jul 22, 2016 at 3:11 PM, Peter Uhnak wrote:
On Fri, Jul 22, 2016 at 11:55:46AM +0800, Ben Coman wrote:
I'm not sure what the roadmap is for git integration, but
Hi,
This flow is taken into account in the new iceberg... I cannot go into details
because I'm still on holidays (and no internet) until Monday... And Nico is
also taking some days.
Anyway, yes... We had this flow in mind (and others, of course) when we worked
in the use cases we want to
On Fri, Jul 22, 2016 at 09:14:25PM +0800, Ben Coman wrote:
> On Fri, Jul 22, 2016 at 3:11 PM, Peter Uhnak wrote:
> > On Fri, Jul 22, 2016 at 11:55:46AM +0800, Ben Coman wrote:
> >> I'm not sure what the roadmap is for git integration, but just a use case
> >> that occurs to me
On Fri, Jul 22, 2016 at 04:11:32PM +0200, Peter Uhnak wrote:
> On Fri, Jul 22, 2016 at 09:14:25PM +0800, Ben Coman wrote:
> > On Fri, Jul 22, 2016 at 3:11 PM, Peter Uhnak wrote:
> > > On Fri, Jul 22, 2016 at 11:55:46AM +0800, Ben Coman wrote:
> > >> I'm not sure what the
First you open a bug report , then you do what Peter said and you attach
your pull request to that bug report. Github will do most of this for you ,
the only tricky part is to add the remote so each time you do git pull you
pull also from the original repo.
Generally you should use as much as you
On Fri, Jul 22, 2016 at 3:11 PM, Peter Uhnak wrote:
> On Fri, Jul 22, 2016 at 11:55:46AM +0800, Ben Coman wrote:
>> I'm not sure what the roadmap is for git integration, but just a use case
>> that occurs to me while I work "a bit with git" for the first time from
>> Pharo.
>>
On Fri, Jul 22, 2016 at 09:57:37AM +, Dimitris Chloupis wrote:
> No.
>
> It may surprise you but pull requests having nothing to with code review,
> they are just a formality.
>
> To understand pull requests you have to understand character of the person
> that created git, Linus , the man
No.
It may surprise you but pull requests having nothing to with code review,
they are just a formality.
To understand pull requests you have to understand character of the person
that created git, Linus , the man behind Linux. He is not exactly the most
easy going person, and he wanted a VCS
Ah yes that's the tool.
Generally speaking if you plan to contribute to the repo very frequently
being a contributor will allow you to commit directly since in most cases
you will be familiar with the repo and know what you doing.
I see a pull request as a way to moderate commits by people that
On Fri, Jul 22, 2016 at 11:55:46AM +0800, Ben Coman wrote:
> I'm not sure what the roadmap is for git integration, but just a use case
> that occurs to me while I work "a bit with git" for the first time from
> Pharo.
>
> I install a project via a Baseline from git and makes a small improvement.
Actually you can , there was even a tool for Pharo that uses the github api
to do most common git actions, github api does not need git installed
because it does everything online. Alternatively you can use GitHub web GUI
, you will have to be added to the repo as contributor though to have the
I'm not sure what the roadmap is for git integration, but just a use case
that occurs to me while I work "a bit with git" for the first time from
Pharo.
I install a project via a Baseline from git and makes a small improvement.
What is the easiest way to contribute back? I can't push back to the
14 matches
Mail list logo