Reputation
1,532
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
5 13
Newest
 Yearling
Impact
~149k people reached

  • 0 posts edited
  • 6 helpful flags
  • 56 votes cast
Jan
7
comment Branching breaks continous integration?
You mix and substitute rather orthogonal things. 0 merge conflict != 0 faulty unit-test, successful merge != successful code
Jan
4
comment Advice: Developing two projects where one is an extension of the other
Easy... Set of dependent-features (even in pure linear case)
Jan
4
comment Git-friendly spreadsheet format?
@AlexanderGladysh - Meld, xmldiff or How can I diff two XML files? topic on SU
Jan
4
comment Advice: Developing two projects where one is an extension of the other
BTW - NVIE-model is real nightmare in real-life with big project
Jan
4
answered Advice: Developing two projects where one is an extension of the other
Jan
4
comment Git-friendly spreadsheet format?
@AlexanderGladysh - just use The Right Tool (tm). For XML it's Altova DiffDog. It's not a Git problem per se, but used differ-merger, which can be extension-specific
Jan
4
comment Git-friendly spreadsheet format?
@AlexanderGladysh - 1. LibreOffice works on Linux. 2. XML is not "MS-bullshit"
Dec
19
answered Wiki/markup in enterprise as documentation
Dec
7
comment Is there tool agnostic terminology for source control activities?
@mattnz - it's a question to hypothetical "Acme RCS 1.0"... Conventional terminology (I think) exist - everybody here, from different today's SCMs, understand users, when (if) they use "check-in" as synonym for "commit". But less part can grok Git-boys, when they start to speak on "gitish" exclusively
Dec
7
comment Is there tool agnostic terminology for source control activities?
@kaz - "but it can be not repo (in CVCS), and local repo can be not .< whatever > subdir in WC", sorry, if you want fair play here. Git working directory and repository are separate objects
Dec
7
answered Looking for best practice for version numbering of dependent software components
Dec
6
comment Is there tool agnostic terminology for source control activities?
Gitboys... Oh, God, no, please!!! Except fact of unwanted ads here, Git actively refuse to use conventional revision control terminology. "Sorry, you use checkout to revert a commit? And checkout also switches between branches? revert is like a merge? WTF?" (c) André Pang
Dec
6
comment Is there tool agnostic terminology for source control activities?
@Kaz - in Bazaar, "checkout" exist in two forms: verb and noun. Verb meaning is equal to other "conventional" SCMs: ... each person should use the checkout command to create their local checkout, i.e. the sandbox in which they will make their changes..."
Dec
6
comment Is there tool agnostic terminology for source control activities?
@Kaz: WTF??? Local repo in git physically - .git dir inside Working Copy
Dec
5
comment Is there tool agnostic terminology for source control activities?
@mouviciel: [clearcase] have ~1 q/day here, 5% (5.2%)in UK job-offers. First-class? Vs Subversion - 45.3%, TFS - 21.3%, Git - 16.2%???
Dec
5
comment Is there tool agnostic terminology for source control activities?
... and Bazaar and Fossil. >50% of market share can't be "misleading", kid!
Dec
5
comment Is there tool agnostic terminology for source control activities?
update is equal in SVN and Mercurial. svn up ID == hg up ID: svn - "Bring changes from the repository into the working copy", Mercurial - "Update the repository's working directory to the specified changeset". RTFM
Dec
5
comment Is there tool agnostic terminology for source control activities?
@MasonWheeler - checkout is initial getting of code from Repository into Working Copy. Update is traversing over history of Revisions and changing active point in Working Copy
Dec
5
answered Is there tool agnostic terminology for source control activities?
Nov
30
answered Strategy for versioning on a public repo