So, I'm trying to checkout just the TestNG plugin from the Netbeans contrib repository. (Or is it module? I'm new to Mercurial, so I don't really know the lingo yet.) When I run the following command... hg clone http://hg.netbeans.org/main/contrib/ ...I get the entire repository, which contains all of the the contrib plug-ins. Is it possible to just pull this location? http://hg.netbeans.org/main/contrib/file/tip/testng/ Thanks!
What is the best way to achieve DevOps with XPages. Multiple Developers working as a team, On Premises Servers [Dev, QA, Prod] can we replicate to Bluemix? Source Control Automated Testing UI / Application, Unit testing business logic with testing framework, Automated Deployment IDE/Tools Domino Designer; are there other ways? Note: Use of Views when the data is in a NSF, otherwise data is in the cloud, or SQL. No Forms or other classic Notes design elements. What are your approaches to this?
I am student, and very new to version control software so I am having trouble figuring this out. I am using a Google code Git repository. To access this repository I am using Git Bash on Windows 7. The problem is that when I reach the push step, I am not being prompted for a password. For example: First I set global variables like this: git config --global user.name "Your Name" git config --global user.email firstname.lastname@example.org Cloned $ git clone https://UserName@code.google.com/p/repository/ Then I made changes to files / added new files etc. and added $ git add . Committed $ git commit -m
I'm new to D3js and before getting started I want to understand how versions for the core and plugins are managed so I don't find myself stuck with an old unsupported versions or using something that's too experimental. If I look at the release history I see that v4 was introduced back in Jun 2016 (https://github.com/d3/d3/releases?after=v4.1.0) and v5 in Jan 2018 (https://github.com/d3/d3/releases?after=v5.0.1). Yet, when I look at D3js code on the gallery (https://github.com/d3/d3/wiki/Gallery), I see that most of it is based on v3 which is 2 major releases behind. For instance if I take a
So I have my subversion repository stored on some cloud (for example code.google.com) but due to various reasons I need to make my code non-public. I decided I needed to download the entire repository and migrate to my own svn server. So I went about using: svnsync init DEST SRC svnsync sync DEST And it took about 0.5 seconds for each revision of the repo! Luckily my repo only had like 200 revisions... so a couple of minutes to wait. But what about mature projects that have 200,000 or 2,000,000 revisions! ... 2e6 * 0.5 / 60 / 60 / 24 ~ about 11 days! Is there anything faster than "svnsync" to
I'm trying to figure out whether a merge conflict was responsible for a bug, but I'm having difficulty because I'm not clear on how conflict resolution affects git blame. Let's say I have a file in master: a(); b(); c(); I modify it in master: a(); d(); c(); but so does a co-worker, and they modify it differently, in a separate branch which they then merge in to master: a(); e(); c(); Can resolving that conflict affect the blame? In other words, if my co-worker resolves the conflict by going with my version: a(); d(); c(); and I git blame the d(); line, who will be blamed: me or my co-worker
We have two Git repositories. Repo 1. Commits: A, B, C. This repository was created from SVN history. Repo 2. Commits: D, E, F. This repository was created without SVN history, just by using the working copy (as of commit C) which became the commit D. In another words, the file trees of the commits C und D are the same. Now, we want to merge both repositories so we have the full history in one repository. Is there a way to "copy/rebase/something else" all the commits E..F onto C?
Let's say you want to show the source code for a settings file but don't want 3-4 lines to show up in the public source code. Do you just manually replace those variables or are there some tricks you use, like including them in yet another separate file and including that in the main conf? Or is it more common to just not track and include that file in the repo?
I have a file I need to move that's already under perforce. Once moved it needs some editing - update the package, etc - appropriate to its new location. Should I submit the move changespec and then reopen it for edit, or can I do this in one go? If so, what is the appropriate sequence of events?