On Mar 11, 2014, at 1:18 PM, Christopher Maynard
christopher.mayn...@gtech.com wrote:
If possible, add some information/basic steps on a few more topics as well?
For example:
1) How do you undo a commit, or undo part of a commit?
You can reset the head, but I really think going there
On Tue, Mar 11, 2014 at 6:47 PM, Hadriel Kaplan
hadriel.kap...@oracle.com wrote:
4) How do you know if someone has a fix or not? With subversion, they'd
indicate they're running svn r51234, for example, and then you could tell
them that they need to update to at least r52345. With git, how
On Tue, Mar 11, 2014 at 7:01 PM, Roland Knall rkn...@gmail.com wrote:
On Tue, Mar 11, 2014 at 6:47 PM, Hadriel Kaplan
hadriel.kap...@oracle.com wrote:
4) How do you know if someone has a fix or not? With subversion, they'd
indicate they're running svn r51234, for example, and then you could
On Tue, Mar 11, 2014 at 2:01 PM, Roland Knall rkn...@gmail.com wrote:
Git commit ids differ
between different people (each clone may create their one)
Not technically true. If I make a commit with SHA x, push it, and it
gets submitted, then it is true that the final SHA in master will be y
!=
On 11 March 2014 20:35, Evan Huus eapa...@gmail.com wrote:
On Tue, Mar 11, 2014 at 2:01 PM, Roland Knall rkn...@gmail.com wrote:
Git commit ids differ
between different people (each clone may create their one)
Not technically true. If I make a commit with SHA x, push it, and it
gets
On Mar 11, 2014, at 1:35 PM, Evan Huus eapa...@gmail.com wrote:
Not technically true. If I make a commit with SHA x, push it, and it
gets submitted, then it is true that the final SHA in master will be y
!= x. However, the next time I pull then I will get SHA y as well.
They x and y
On Tue, Mar 11, 2014 at 4:47 PM, Guy Harris g...@alum.mit.edu wrote:
On Mar 11, 2014, at 1:35 PM, Evan Huus eapa...@gmail.com wrote:
Not technically true. If I make a commit with SHA x, push it, and it
gets submitted, then it is true that the final SHA in master will be y
!= x. However, the
On Tue, Mar 11, 2014 at 4:42 PM, Graham Bloice
graham.blo...@trihedral.com wrote:
On 11 March 2014 20:35, Evan Huus eapa...@gmail.com wrote:
On Tue, Mar 11, 2014 at 2:01 PM, Roland Knall rkn...@gmail.com wrote:
Git commit ids differ
between different people (each clone may create their one)
On Mar 11, 2014, at 1:42 PM, Graham Bloice graham.blo...@trihedral.com wrote:
In any case I don't think this fulfils the initial question. Previously we
could say to users that an issue was fixed in svn r and they would
know that any rev later than that was good. I don't understand
On 11 March 2014 20:50, Evan Huus eapa...@gmail.com wrote:
On Tue, Mar 11, 2014 at 4:42 PM, Graham Bloice
graham.blo...@trihedral.com wrote:
On 11 March 2014 20:35, Evan Huus eapa...@gmail.com wrote:
On Tue, Mar 11, 2014 at 2:01 PM, Roland Knall rkn...@gmail.com wrote:
Git commit ids
On Tue, Mar 11, 2014 at 4:55 PM, Guy Harris g...@alum.mit.edu wrote:
On Mar 11, 2014, at 1:42 PM, Graham Bloice graham.blo...@trihedral.com
wrote:
In any case I don't think this fulfils the initial question. Previously we
could say to users that an issue was fixed in svn r and they
On Tue, Mar 11, 2014 at 4:58 PM, Graham Bloice
graham.blo...@trihedral.com wrote:
On 11 March 2014 20:50, Evan Huus eapa...@gmail.com wrote:
On Tue, Mar 11, 2014 at 4:42 PM, Graham Bloice
graham.blo...@trihedral.com wrote:
On 11 March 2014 20:35, Evan Huus eapa...@gmail.com wrote:
On
On 11 March 2014 21:06, Evan Huus eapa...@gmail.com wrote:
On Tue, Mar 11, 2014 at 4:58 PM, Graham Bloice
graham.blo...@trihedral.com wrote:
On 11 March 2014 20:50, Evan Huus eapa...@gmail.com wrote:
On Tue, Mar 11, 2014 at 4:42 PM, Graham Bloice
graham.blo...@trihedral.com wrote:
On
On Tue, Mar 11, 2014 at 5:11 PM, Graham Bloice
graham.blo...@trihedral.com wrote:
On 11 March 2014 21:06, Evan Huus eapa...@gmail.com wrote:
On Tue, Mar 11, 2014 at 4:58 PM, Graham Bloice
graham.blo...@trihedral.com wrote:
On 11 March 2014 20:50, Evan Huus eapa...@gmail.com wrote:
On
On Mar 11, 2014, at 2:06 PM, Evan Huus eapa...@gmail.com wrote:
On Tue, Mar 11, 2014 at 4:58 PM, Graham Bloice
graham.blo...@trihedral.com wrote:
That doesn't help users who only install, not build as their copy of
Wireshark doesn't have a list of SHA (or does it?).
They only way I can
On Mar 11, 2014, at 2:13 PM, Evan Huus eapa...@gmail.com wrote:
It's not. But if they ask, it's relatively easy for somebody with git
to be able to find out.
Somebody with Git and the repository.
That's why I suggested that they be able to ask some*thing* with Git and the
repository,
On Mar 11, 2014, at 5:15 PM, Guy Harris g...@alum.mit.edu wrote:
Perhaps we should have a page on some wireshark.org where a user can enter
some identifier for an automated build and an SHA hash for a commit and find
out whether that build has that commit, and perhaps also say take me to
On Tue, Mar 11, 2014 at 5:34 PM, Hadriel Kaplan
hadriel.kap...@oracle.com wrote:
On Mar 11, 2014, at 5:15 PM, Guy Harris g...@alum.mit.edu wrote:
Perhaps we should have a page on some wireshark.org where a user can enter
some identifier for an automated build and an SHA hash for a commit and
On Mar 11, 2014, at 5:38 PM, Evan Huus eapa...@gmail.com wrote:
On Tue, Mar 11, 2014 at 5:34 PM, Hadriel Kaplan
hadriel.kap...@oracle.com wrote:
Googling around a bit for this issue - because other apps must have this
same problem and their users - shows people either creating a ton of
19 matches
Mail list logo
