It seems to me that all it does is add an extra layer
Yes indeed. And that's a good thing, because it allows you to commit
often and very granularly.
I read that you were preparing everything for a committing one big
change to Subversion.
The Git workflow is a bit different.
In Git you would:
On the command line, I use Cygwin which is easier because I use a lot of
other command line tools there.
But I couldn't get tab completion to work for the git commands. These do
work as expected in Msysgit.
Also, if you're an IntelliJ user: their Git integration is very, very good.
Though you h
Not sure it helps but if you're talking about directory/file completion
Thanks, but I was referring to the git commands, branch names, remotes,
etc.: labels related to Git and the Git repo. Directory/file completion
works fine.
There is a Git tab completion package in Cygwin, but I installed it
Hi Erik,
I can't seem to find much information for non-committers (except for the
GitHub line at the end).
Will that be on a different page?
Regarding the GitHub pull requests: I thought this was one of the major
reasons to move to Git; to provide developers an easy means of
contributing small
I can't seem to find much information for non-committers
On second read I found "7b) Everyone else: create a patch".
I didn't see it the first time because it was listed under "*Committers:
working on the code*"
Perhaps this could be made more apparent.
Max
How would that work, if you don't mind explaining?
On the non-comitter's side:
- A non-committer forks the GitHub repo
- He now has a complete copy of this repo in his own account
- He clones his own fork to work on it locally
- He works locally, makes some commits, pushes to his fork, makes some
It's not just a click on the accept pull request on github.
I was afraid it would be harder than that with an Apache project :(
Can't he clone directly the GitHub Repo ?
Yes he can, but he will not be able to generate a pull request like
that, because he has no write access to the remote repo.
which branch(es) will non-committers have to target?
I would say, its own branch, I mean a branch with the name of the
relative issues in the JIRA
I don't think it is possible to directly target a new branch. The target
branch must be an existing one.
I don't know if the committer handling th
Hi Mark,
Interesting idea. I was thinking: wouldn't it be more convenient to let
all that happen through one property of type Array?
Lets' call it `disabledButtons:Array`; it would disable the items in the
Array en enable those not in the Array.
That way this code from your test app
Sorry for the delay.
I guess my main argument in favour of the array attribute was the
convenience of being able to enable/disable buttons purely through MXML
+ data binding.
But I have other arguments ;) I'm not sure why having another
"dataProvider" would be inconvenient. The `selectedItem
10 matches
Mail list logo
